• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    The invention proposes to automate the detection of a configuration change of an onboard equipment (3) as well as the reloading of the appropriate software configuration in said equipment and concerns an automatic recharging system (1) comprising: a transmitter (7) associated with said equipment and adapted to emit a configuration frame comprising a set of identifiers of the current hardware and / or software configuration of said equipment, - a detector (9) adapted to capture said configuration frame and to detect a change hardware and / or software configuration of said equipment, - a software loader (11) adapted to automatically reload a set of appropriate software elements in said equipment according to the detected configuration change.
    公开号:FR3026509A1
    申请号:FR1459125
    申请日:2014-09-26
    公开日:2016-04-01
    发明作者:Anne Frayssignes；Marc Cramoisan
    申请人:Airbus Operations SAS；
    IPC主号:
    专利说明:

    [0001] TECHNICAL FIELD OF THE INVENTION The present invention relates to the field of download and more particularly relates to an automatic reloading of software on an on-board and replaceable equipment of an aircraft. An aircraft comprises a plurality of downloadable onboard equipment performing functions specific to the aircraft. These onboard equipment are replaceable and are generally called calculators or "replaceable equipment" LRU (Line Replaceable Units). Currently, when an onboard equipment is defective, it is removed from the aircraft, sent to the maintenance center to be tested and possibly repaired. Defective equipment is then replaced by repaired equipment or new equipment. At the maintenance center, a dedicated test software for testing the defective equipment is installed instead of the operational software already loaded into the equipment. After repairing the equipment, the test software is removed and the equipment is often kept empty or reloaded with minimal configuration software. It is very rare that the operational software is reinstalled in the equipment because it is difficult to anticipate the software configuration that the equipment will have to have when it is reinstalled in an aircraft. In the case where the equipment has not been reloaded or has been partially reloaded, the maintenance operator must reload the missing software in the equipment on board the aircraft. After returning the equipment to its slot, the maintenance operator must perform a plurality of selections on an interface of a portable or on-board download management device to select the target to download and install the appropriate software into the equipment. target. Then he must check the new configuration of the equipment, validate his actions and close his jobcard. All these actions require a significant amount of time and are performed while the aircraft is immobilized thus generating delays and additional costs. Even in the very rare case where the operational software has been reinstalled in the equipment, the maintenance operator must still check the configuration of the equipment.
    [0002] Similarly, in the case where the defective equipment needs to be replaced by other equipment not including or only part of the operational software, the same actions as previously require to be performed by the maintenance operator. In addition, in the case where the defective equipment is replaced by other non-standard equipment requiring different software, the maintenance operator must ensure the authorized software parts, retrieve the corresponding software, load them into the equipment and by therefore, requiring even more time. The object of the present invention is therefore to overcome the aforementioned drawbacks by proposing a method and a system for automatically reloading appropriate software on an on-board equipment thus reducing the downtime of the aircraft and costs. OBJECT AND SUMMARY OF THE INVENTION The present invention aims at automating the detection of a configuration change of an on-board equipment and the reloading of the appropriate software configuration in said equipment. The invention relates to a method and system for automatically reloading software into an aircraft's replaceable on-board equipment, said equipment being reinstalled on the aircraft after having been removed and repaired or being new equipment installed on the aircraft for replace a defective equipment previously removed, said system comprising: a transmitter associated with said equipment and adapted to emit a configuration frame comprising a set of identifiers of the current hardware and / or software configuration of said equipment, a detector adapted to capture said equipment configuration frame and to detect a hardware and / or software configuration change of said equipment, - a software loader adapted to automatically reload a set of appropriate software elements in said equipment according to the configuration change detected. Thus, this system of automatic reloading of software on an on-board equipment makes it possible to reduce the time and the costs of replacement of a defective equipment. BRIEF DESCRIPTION OF THE DRAWINGS Other features and advantages of the system and method according to the invention will emerge more clearly on reading the description given below, by way of indication but without limitation, with reference to the appended drawings in which: FIG. . 1 schematically illustrates an automatic software reloading system in an on-board equipment of an aircraft, according to one embodiment of the invention; FIG. 2 schematically illustrates an automatic software reloading system in an on-board equipment of an aircraft, according to a first preferred embodiment of the invention; FIG. 3 schematically illustrates an example of a method for automatically reloading software in an aircraft on board equipment, according to the first embodiment of the invention; FIG. 4 schematically illustrates another example of a method for automatically reloading software in an aircraft on board equipment, according to the first embodiment of the invention; FIG. 5 schematically illustrates an automatic software reloading system in an aircraft equipment of an aircraft, according to a second preferred embodiment of the invention; - Figs. 6A and 6B schematically illustrate two variants of a connection mechanism according to the second embodiment of the invention; and - FIG. 7 schematically illustrates an example of a method of automatic reloading of software in an aircraft onboard equipment, according to the second embodiment of the invention.
    [0003] DETAILED DESCRIPTION OF EMBODIMENTS The principle of the invention consists in particular in automating the reloading of software on an on-board and replaceable equipment of an aircraft. Fig. 1 schematically illustrates a system 1 of automatic software reloading in a device 3 on board an aircraft 5, according to one embodiment of the invention. The onboard equipment 3 is a replaceable equipment LRU and downloadable calculator type (for example, a flight control computer, a hydraulic control computer, etc.). Each device 3 is identified by a Serial Number (SNR) serial number as well as hardware functional item numbers (HW FIN) including HW PNR (Hardware Part Numbers) hardware numbers, as well as software identifiers. Software Functional item numbers (SW FIN) with SW PN software part numbers (Software Part Numbers). Each of these identifiers is unique and invariant. For example, each software functional identifier SW FIN is an invariant that uniquely and unambiguously identifies the position of a software embedded on the aircraft 5. Thus, each equipment 3 can be identified by a set of identifiers defining its hardware configuration. and / or software. When equipment 3 is reinstalled on the aircraft 5 after being removed and repaired or when new equipment is installed on the aircraft to replace defective equipment previously removed, the system 1 reloading according to the invention is adapted to automatically reload the missing appropriate software items in the equipment. Indeed, according to the invention, the charging system 1 comprises hardware and / or software means comprising a transmitter 7, a detector 9, and a software charger 11.
    [0004] The transmitter 7 is associated with the equipment 3 and can be an integral part of the equipment or its environment. It is adapted to emit a configuration frame comprising a set of identifiers of the current hardware and / or software configuration of the equipment. By "current configuration" is meant that which defines the equipment 3 on the issue date. The detector 9 is an onboard means adapted to capture the configuration frame transmitted by the transmitter 7. The detector 9 is configured to detect any hardware and / or software configuration change of the equipment 3 thus making it possible to identify the fact that this last was removed and then reinstalled or the equipment is new and replaces the one previously installed. More particularly, the detector 9 comprises a receiver 91, a comparator 92, a trigger 93 and a recorder 94. The receiver 91 is adapted to capture each hardware and / or software configuration frame of the equipment 3 transmitted by the transmitter 7 .
    [0005] The recorder 94 is adapted to store the identifiers of the current configuration. For example, the identifiers are stored in an internal table describing the history of the identifiers with the date of receipt of these identifiers. The comparator 92 is adapted to compare the identifiers of the current configuration of the equipment 3 with those of the previous configuration in order to detect any hardware and / or software configuration change of the equipment. Thus, the comparator 92 compares each current configuration frame with that received previously. If the current frame includes the same identifiers as the previous frame, then the comparator 92 concludes that the equipment 3 has not been removed and only updates the date of the identifiers in the internal history table of the recorder. On the other hand, if the current frame does not include identifiers and / or does not include a part of the identifiers, then the comparator 92 concludes that the equipment 3 is new (if the SNR serial number and / or part numbers HW PNR hardware has been changed) or that it has been reinstalled after being removed (if only SW PNR software part numbers have changed). In this case, the current identifiers are saved and the trigger 93 triggers the loading of the appropriate software. Indeed, the trigger 93 is adapted to transmit to the software loader 11 a trigger signal indicating for example the previous and current configurations of the equipment thus triggering the download of the set of appropriate software elements in said equipment 3 in function the configuration change detected. Advantageously, the software loader 11 is adapted to reload the set of appropriate software elements in the equipment 3 in an appropriate order. Alternatively, the software loader 11 is adapted to reload the set of appropriate software elements in the equipment 3 in any order. In this case, it is the equipment 3 which is configured to reorganize the set of software elements according to an appropriate loading order.
    [0006] Advantageously, the system 1 comprises an embedded software storage device 13 (repository). The software loader 11 is then adapted to recover the set of software elements from this embedded software storage device 13. It will be noted that, in the case where certain software elements are not included in the on-board storage device, the software loader 11 is adapted to recover via missing devices or means of communication 15 from a storage device or service. software on the ground. In addition, in the case where the system 1 does not include an onboard software storage device 13, the software loader 11 is also adapted to recover via the communication means 15 the set of software elements from the storage device. 17 of software on the ground. Advantageously, the software loader 11 is adapted to transmit after reloading the set of appropriate software elements in the equipment 3 a notification to a maintenance operator 19 confirming the completion of reloading.
    [0007] Moreover, after the loading of the appropriate software elements, the equipment 3 is adapted to restart automatically. After the restart of the equipment, the transmitter 7 is adapted to emit a new configuration frame comprising the current hardware and / or software configuration identifiers.
    [0008] In addition, the detector 9 is adapted to verify that the equipment 3 has the appropriate hardware and / or software configuration. The detector 9 is also adapted to perform a validation and a history of the new configuration. For example, logging consists of storing all new identifiers in the first row of the internal history table by shifting all other rows.
    [0009] Fig. 2 schematically illustrates an automatic software reloading system in an on-board equipment of an aircraft, according to a first preferred embodiment of the invention. According to this first embodiment, the transmitter 7 is integrated in the onboard equipment 3. The transmitter 7 is for example a computer application that is implemented by the processor or the equipment processing means 3. When the equipment 3 is installed in its housing 21 and thus powered, the transmitter 7 is adapted to transmit at successive dates (for example periodically every minute) a sequence of frames 23 configuration. Each frame 23 comprising, on the issue date, the hardware and / or software configuration identifiers of the equipment item 3. Thus, each current frame 23 emitted by the transmitter 7 is picked up by the detector 9 and compared to the frame received. previously to detect any hardware and / or software configuration changes to the equipment. It will be noted that if the transmission is periodic and the detector 9 no longer receives frames for a time longer than the transmission period, it concludes that the equipment has been removed. The detector 9 waits for the reception of new frames before concluding that the equipment 3 has been reconnected or that a new equipment has been connected according to the identifiers included in the frame.
    [0010] Fig. 3 schematically illustrates an example of a method of automatic software reloading in an aircraft onboard equipment, according to this first embodiment of the invention. In step E1, a maintenance operator 19 removes a defective onboard equipment 3 after the landing of the aircraft 5. By way of example, the equipment has been previously detected defective during the flight by an on-board monitoring system. (not shown) and a message was sent to the ground for replacement of the equipment with new equipment. In step E2, the maintenance operator 19 installs the new equipment 3 he has procured before landing the aircraft 5 in its housing 21 corresponding to the place of the defective equipment that has been removed. in step E1. In step E3, the maintenance operator 19 restores the power supply for the new equipment 3. In step E4, the new equipment 3 begins to periodically transmit a configuration frame 23 LRU CONF FRAME comprising a set of identifiers in the form of triplets for hardware identifiers and pairs for software identifiers. For example, the configuration frame includes a hardware identifier FIN HW associated with a new PNR part number HW NEW and a _ _ _ new serial number SNR _ HW _NEW and each of the N software identifiers END SW1 END SWN is associated with a new PNR software part number SW1 NEW PNR SWN NEW The configuration frame can then have the following form: [FIN_HW = PNR HW NEW & SNR HW NEW], [FIN_SW1 = PNR SW1 NEW], ..., [FIN_SWN = PNR_SWN_NEW ].
    [0011] In step E5, the detector 9 acquires the configuration frame LRU CONF FRAME, retrieves each identifier (pair / triplet) and updates the values of the hardware and software PNR / SNR identifiers in an internal history table 95 which includes a line or position by part number. Next, the detector 9 compares each of the hardware identifiers PNR HW NEW & SNR HW NEW and software _ _ _ _ PNR SW1 NEW PNR SWN NEW of the current frame to each of the hardware identifiers PNR_HW_OLD & SNR_HW_OLD and software PNR_SW1_OLD, ..., PNR_SWN_OLD corresponding already stored on the last line of the internal table 95 and associated with the previous equipment. In particular, it is assumed that according to this example the defective equipment has been replaced by new standard equipment 3 or equivalent. So, the hardware SNR serial number of the new equipment is different from that of the previous equipment but the hardware part number PNR does not change. Furthermore, it is assumed that at least one element of the FIN_SW software identifiers hosted by the new equipment is different from that hosted by the removed equipment. Thus, the detector 9 detects a hardware configuration change SNR and software FIN_SW equipment 3 and determines the software elements that must be reloaded in the new equipment. In step E6, the detector 9 transmits to the software loader 11 a trigger signal indicating, for example, the previous and current configurations of the equipment thus indicating to them the software elements which must be recharged in the equipment 3. In particular, it signals to the software loader 11 that the software identifiers FIN_SW1 ... END_SWN of the equipment referenced by the hardware identifier [FIN_HW = PNR_HW_NEW & SNR_HW_NEW] must be loaded with software elements PNR_SW1_OLD, ..., PNR_SWN_OLD associated with the previous equipment with the same hardware part number PNR_HW_NEW = PNR_HW_OLD.
    [0012] In the case where the equipment 3 does not need to be downloaded in a particular order, then we go to step E7a. However, in the case where the equipment 3 needs to be downloaded in a specific order, then we go to step E7b. In step E7a, the software loader 11 knows that the FIN_HW equipment concerned by the loading is capable of downloading the SW element or software elements in any order and that no software element other than those indicated by the detector 9 does not need to be reloaded in the equipment 3, the latter itself being adapted to rearrange the set of downloaded software elements according to an appropriate loading order. Thus, the software loader 11 can reload at step E7a the set of software elements in the equipment 3 without worrying about the loading order.
    [0013] In step E7b, the software loader 11 is adapted to memorize in which direction it is necessary to reload the set of software elements in the equipment 3. In fact, the software loader 11 determines which software identifiers FIN_SW are concerned and uses templates ("LRU RESTORE PATTERN") previously saved in a dedicated memory. This kind of models is described in the patent application FR1352194 of the applicant. In case the software loader 11 realizes that a certain software reference SWX_PNR is missing, then it asks the detector 9 to provide it with the missing information. The latter then returns the corresponding value PNR_SWX_OLD to the software loader 11 which in turn acknowledges receipt. Thus, the software loader 11 can reload in step E7b the set of software elements in the equipment 3. In step E8a or E8b, the software loader 11 retrieves the software elements that must be reloaded in the equipment 3. Note that in the case where the aircraft 5 comprises a device or onboard storage space 13 (repository) in which all the software of the onboard equipment are stored, then, the software loader 11 recovers for each of the software invariants, the software elements (or software parts) that must be reloaded in the equipment 3 (step E8a). On the other hand, in the case where the aircraft 5 does not include an onboard storage space, then the software loader 11 uses the communication means 15 of the aircraft to send requests to a ground service 17 FLSGR (Field Loadable Software Repository) to retrieve copies of all missing software items to be loaded into the equipment 3 and acknowledge receipt after receiving these copies (step E8b).
    [0014] In step E9a or E9b, the software loader 11 reloads the set of software elements in the targeted equipment 3, guided if necessary by the "LRU RESTORE PATTERN" models. More particularly, in step E9a the software loader 11 builds a list of items to be loaded from the elements established in step E7a and recovered in step E8a or E8b.
    [0015] In step E9b, the software loader 11 retrieves the "LRU RESTORE PATTERN" models associated with FIN-HW, updates them with the elements established in step E7b and recovered in step E8a or E8b. Then, the software loader 11 executes the "LRU RESTORE PATTERN" model step by step according to an electronic service bulletin eSB (electronic Service Bulletin). The execution step by step is described in particular in the patent application FR1352194 of the applicant. In step E10 the software loader 11 issues a notification to the maintenance operator 19 indicating that the automatic reloading operation is complete.
    [0016] In step E11, the equipment 3 restarts automatically and starts issuing periodically a new CONF FRU configuration frame including the new hardware and / or software configuration identifiers for example in the following form: [FIN_HW = PNR HW NEW & SNR HW NEW], [FIN_SW1 = PNR SW1 OLD], ..., [FIN_SWN = PNR_SWN_OLD]. In step E12, the detector 9 captures the new configuration frame LRU CONF FRAME and compares each PNR / SNR value of the current frame (ie received last) with the corresponding values of the previous frame previously stored in order to verify that the 3 targeted equipment has the desired configuration. In step E12, the detector 9 verifies that the targeted equipment 3 has been restored or reconfigured according to the appropriate hardware and / or software configuration of the removed equipment. The detector 9 then validates this new configuration and all the new elements are stored in the first line of the internal history table by shifting all the other lines (ie, the line N shifts to N-1, the line N-1 to N -2 and the line N-2 is lost). In step E13, the detector 9 transmits to the maintenance operator 19 the new configuration of the equipment so that the latter can close his job card. As a variant, the new configuration is sent to an application for automatic filling of the job tickets.
    [0017] In step E14, the job ticket is closed by the maintenance operator 19 or by the automatic filling application. Fig. 4 schematically illustrates another example of a method for automatically reloading software in an aircraft on board equipment, according to the first embodiment of the invention. According to this example, it is assumed that the defective equipment has been replaced by new non-standard equipment. In this case, the SNR hardware serial number and the PNR hardware part number of the new equipment are different from that of the previous equipment.
    [0018] Steps E1 to E5 and E7a to E13 are identical to those of FIG. 3. As before, it is also assumed that at least one element of the FIN_SW software identifiers hosted by the new equipment 3 is different from that hosted by the removed equipment. Thus, the detector 9 detects a hardware configuration change SNR and software FIN_SW equipment.
    [0019] In step E61, the detector 9 transmits to the software loader 11 a trigger signal indicating that it must reload all the software elements FIN_SW1 ... END _SWN in a device having a new hardware identifier and that it is necessary to provide the list of these software elements. In step E62, the software loader 11 sends a request to a ground service 18 to provide a list of the software part numbers to be installed on the new equipment 3 equipped with a new hardware part number SNR_HW_NEW. Once it has the list of new software part numbers, it acknowledges receipt and recovers as previously all the software elements either from the on-board storage device 13 (step E8a) or from the FLSGR service 17 (step E8b) .
    [0020] Fig. 5 schematically illustrates an automatic software reloading system in an on-board equipment of an aircraft, according to a second preferred embodiment of the invention. This second embodiment applies in the case where the equipment 3 is not suitable for itself transmitting configuration frames. In this case, the equipment 3 is coupled to a transmitter 7 comprising a connection detection mechanism 71, a first RFID tag 72 tagging the equipment 3, a second RFID tag 73 tagging the housing 21 associated with the equipment 3, and management means or an RFID controller 74. An RFID management procedure is described in the French patent application FR1353448 of the applicant.
    [0021] The connection detection mechanism 71 is adapted to detect a reconnection of the equipment 3 in a corresponding housing 21 of the aircraft and to emit a reconnection signal when the equipment has been connected in its housing. This mechanism comprises an electrical circuit provided with a switch that is triggered when the equipment is placed in its housing changing the open or closed state of the circuit. Fig.
    [0022] 6A is an example of this kind of mechanism 71 showing an electrical circuit 75 comprising a switch 76 disposed at the bottom of the housing 21. The circuit 75 is connected wired or wirelessly to the detector 9 or the RFID controller 74. The switch 76 is actuated by the introduction of the equipment 3 in its housing 21 thus closing the electrical circuit 75 which then transmits a binary signal to the detector 9 and / or the RFID controller 74. FIG.
    [0023] 6B is another example of the connection detection mechanism also showing an electrical circuit 75 connected wired or non-wired to the detector 9 and / or the RFID controller 74 and provided with a socket 77 disposed at the bottom of the housing 21. rear of the equipment 3 is equipped with pins 78 which engage in the socket 77 by the introduction of the equipment 3 in its housing 21 thus closing the electrical circuit 75 which then transmits a binary signal to the detector 9 and / or RFID controller 74. The first RFID tag 72 is a radio-label fixed for example by gluing on the equipment 3 with which it is associated. The first RFID tag 72 comprises first identifiers of the hardware configuration PNR_HW & SNR_HW and possibly software configurations of the equipment 3. The second RFID tag 73 is fixed for example by gluing on the housing 21 with which it is associated and is coupled to the first RFID tag 72. The second RFID tag 73 comprises second hardware identifiers FIN_HW equipment 3 to be installed in this housing 21. The information contained in the first 72 and second 73 tags are at least sufficient to allow adequate reloading 3. The RFID controller 74 is installed on the aircraft 5. After reconnecting the equipment 3, the RFID controller 74 is adapted to interrogate the first RFID tag 72 tagging this equipment 3. In response to the request of the RFID controller 74, the first RFID tag 72 is adapted to transmit to the latter the data from the second RFID tag 73 to which it is coupled with insi the data from the first RFID tag 72 itself. Thus, the RFID controller 74 is adapted to recover the first and second configuration identifiers recorded in the first and second RFID tags. In addition, the RFID controller 74 is adapted to transmit a configuration frame including these first and second configuration identifiers of the equipment to the detector 9. FIG. 7 schematically illustrates an example of a method for automatically reloading software in an aircraft on board equipment, according to the second preferred embodiment of the invention. This process is identical to that of FIG. 3 or FIG. 4 with the exception of step E4 which is replaced by steps E41 to E44. Steps E1 to E3 relate to replacing defective equipment with new equipment or installing the same equipment after repair. In step E41, after the installation of a new equipment 3 or the same equipment repaired in its housing 21, a reconnection signal is emitted by the connection detection mechanism 71. In step E42, the detector 9 receives the reconnection signal from the connection mechanism 71 indicating that the equipment 3 has been connected in its housing 21. The detector 9 therefore requests the RFID controller 74 to transmit the identifiers configuration of the equipment. In step E43, the RFID controller 74 excites the first tag 72 which refers to the latter (step E44) the data from the second RFID tag 73 to which it is coupled as well as the data from the first RFID tag 72 itself. Thus, the RFID controller 74 retrieves the hardware identifiers FIN_HW from the second tag 73 and the hardware identifiers PNR _ HW & SNR _HW (and possibly software) from the first tag 72. In step E45, the RFID controller 74 sends a configuration frame including the hardware and possibly software configuration identifiers of the equipment to the detector 9. Then, the steps are identical to the steps E5 to E14 of FIG. 3 or Fig. 4. Thus, the present invention makes it possible to automatically detect a configuration change of an on-board equipment (meaning that it has been removed and then reinstalled on the aircraft) and to automatically reload in said equipment the appropriate software configuration.
    权利要求:
    Claims (10)
    [0001]
    REVENDICATIONS1. A system for automatically reloading software into an aircraft's replaceable on-board equipment, said equipment being reinstalled on the aircraft after being removed and repaired or being new equipment installed on the aircraft to replace defective equipment previously removed, said system being characterized in that it comprises: - a transmitter (7) associated with said equipment (3) and adapted to emit a configuration frame comprising a set of identifiers of the current hardware and / or software configuration of said equipment, - a detector (9) adapted to capture said configuration frame and to detect a hardware and / or software configuration change of said equipment, - a software loader (11) adapted to automatically reload a set of appropriate software elements into said equipment (3). ) depending on the detected configuration change.
    [0002]
    2. The system of claim 1, wherein the detector comprises: a receiver (91) adapted to capture said configuration frame, a comparator (92) adapted to compare the identifiers of the current configuration of the equipment with those of the previous configuration for detecting any hardware and / or software configuration change of said equipment, - a trigger (93) adapted to transmit to the software loader a trigger signal in order to trigger the download of said set of appropriate software elements into said equipment according to the configuration change detected, and - a recorder (94) adapted to record the identifiers of the current configuration. 30
    [0003]
    3. System according to claim 1 or 2, wherein the transmitter (7) is integrated in said equipment (3) embedded and is adapted to transmit at successive dates a sequence of configuration frames, each frame comprising the date of transmitting the current hardware and / or software configuration identifiers of said equipment.
    [0004]
    4. System according to claim 1 or 2, wherein the transmitter comprises: - a connection detection mechanism (71) adapted to detect a reconnection of the equipment in a corresponding housing of the aircraft, - a first RFID tag (72) tagging said equipment and having first configuration identifiers, - a second RFID tag (73) tagging the housing of said equipment and having second configuration identifiers, and - an RFID controller (74) adapted to recover the first and second configuration identifiers from the first and second RFID tags after detecting the reconnection of the equipment, and transmitting said configuration frame including the current configuration identifiers of the equipment on the date of its reconnection in its slot.
    [0005]
    5. System according to claim 4, wherein the connection detection mechanism comprises a switch (76) which is triggered when the equipment is placed in its housing.
    [0006]
    6. System according to any one of the preceding claims, comprising an embedded device (13) for storing software, the software loader (11) being adapted to recover said set of software elements from said embedded software storage device.
    [0007]
    7. System according to any one of claims 5, wherein the software loader (11) is adapted to recover via communication means (15) said set of software elements from a software storage device disposed on the ground .
    [0008]
    8. System according to any one of the preceding claims, wherein the detector (9) is adapted to verify that the equipment has the appropriate configuration and to perform a validation and a history of the new configuration.
    [0009]
    9. Aircraft having a reloading system according to any one of the preceding claims.
    [0010]
    10. A method of automatically reloading software into an aircraft's replaceable aircraft equipment, said equipment being reinstalled on the aircraft after having been removed and repaired or being new equipment installed on the aircraft to replace defective equipment previously removed. , said method being characterized in that it comprises the following steps: - transmission of a configuration frame comprising a set of identifiers of the current hardware and / or software configuration of said equipment, - capture of said configuration frame and detection a hardware and / or software configuration change of said equipment, - automatic reloading of a set of appropriate software elements into said equipment according to the detected configuration change.
    类似技术:
    公开号 | 公开日 | 专利标题
    FR3026509A1|2016-04-01|AUTOMATIC SOFTWARE RECHARGING ON ONBOARD EQUIPMENT
    US20140277831A1|2014-09-18|Method and apparatus for reducing data transfer rates from a vehicle data logger when a quality of the cellular or satellite link is poor
    CN111164440A|2020-05-15|System and method for monitoring and presenting battery information
    WO2015188501A1|2015-12-17|Configuration file updating method, device, system and computer storage medium
    FR2977046A1|2012-12-28|ADVANCED DIAGNOSTIC FOR AIRCRAFT
    FR2990531A1|2013-11-15|METHOD FOR UPDATING AN AIRCRAFT SOFTWARE ABOARD AN AIRCRAFT
    CN109388123A|2019-02-26|Vehicle communication
    EP3267663B1|2020-03-18|Method for updating a plurality of vehicles and ensemble formed by a plurality of railway vehicles and an associated management system
    FR2978264A1|2013-01-25|AN AUTOMATIC SOFTWARE RECHARGING METHOD AND AN AUTOMATIC SOFTWARE RECHARGING DEVICE
    EP2346009A1|2011-07-20|Communication device and method for sealing an equipment
    FR3003365A1|2014-09-19|METHOD AND DEVICE FOR MANAGING SOFTWARE UPDATES OF A SET OF EQUIPMENT OF A SYSTEM SUCH AS A SYSTEM OF AN AIRCRAFT
    EP3257028B1|2020-01-08|Semi-automatic display unit for gas cylinders and associated method
    EP2204713A1|2010-07-07|Method for controlling the integrity of an avionics system and control device for implementing said method
    FR2876814A1|2006-04-21|Electric or electronic system`s fault context recording system for motor vehicle, has two controllers recording fault context data relative to functioning of components, and telematic controller transmitting recorded data to remote server
    FR2952456A1|2011-05-13|Autonomous railway traffic management device, has processing circuit determining passage direction of railway vehicle and controls reading of data by reader and transmission of data towards information server by communication circuit
    EP3690459A1|2020-08-05|Standalone device for monitoring time of use of a generator set, and corresponding generator set and method.
    EP3255442B1|2021-08-25|Method for diagnosing a set of accumulator batteries distributed in a fleet of motor vehicles
    FR3099918A1|2021-02-19|Control device for monitoring the transport of turbomachines on a corresponding vehicle, vehicle, method, and monitoring installation
    FR2973131A1|2012-09-28|METHOD AND DEVICE FOR DETECTING INCOMPATIBILITIES OF LOGIC INTERFACES OF ONBOARD SYSTEM EQUIPMENT
    FR3043611A1|2017-05-19|ELECTRONIC UNIT, SYSTEM COMPRISING SUCH AN ELECTRONIC UNIT AND METHOD FOR UNLOCKING
    EP3764751A2|2021-01-13|Street light for centralised management and associated management method
    FR3103211A1|2021-05-21|Modular on-board system for recording and downloading data from a turbomachine calculator
    FR2959317A1|2011-10-28|Device for detection of characteristic of battery of equipment in vehicle i.e. automobile, has reading unit determining information data to allow estimation of load state of battery based on characteristic represented by determined data
    FR3103926A1|2021-06-04|A method of updating a digital system.
    FR3077038A1|2019-07-26|DIAGNOSTIC SYSTEM AND METHOD FOR ELECTRIC MOTOR VEHICLE LOAD TERMINAL
    同族专利:
    公开号 | 公开日
    US20160092192A1|2016-03-31|
    FR3026509B1|2016-12-09|
    US9612819B2|2017-04-04|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    EP1688840A2|2005-02-04|2006-08-09|Rockwell Automation Technologies, Inc.|System and method for automatically matching programmable data of devices within an industrial control system|
    US20070055470A1|2005-09-08|2007-03-08|Rockwell Automation Technologies, Inc.|RFID architecture in an industrial controller environment|
    US8543671B1|2010-12-30|2013-09-24|United States Automobile Association |Grouped computing device configuration management|FR3058244A1|2016-10-27|2018-05-04|Airbus Operations|CONFIGURATION OF AN ELECTRONIC DEVICE ONBOARD BY READING A RADIO LABEL|US9443358B2|1995-06-07|2016-09-13|Automotive Vehicular Sciences LLC|Vehicle software upgrade techniques|
    US7975491B2|2005-03-17|2011-07-12|Smisson-Cartledge Biomedical Llc|Heat exchange system for a pump device|
    US8138913B2|2007-01-19|2012-03-20|System Planning Corporation|Panel system and method with embedded electronics|
    DE102008062630A1|2008-12-17|2010-06-24|Airbus Deutschland Gmbh|Method for scheduling maintenance operations of systems|
    DE102009041599A1|2009-09-15|2011-04-14|Airbus Operations Gmbh|A control device, input / output device, connection switching device and method for an aircraft control system|
    FR2978264B1|2011-07-18|2014-06-27|Airbus Operations Sas|AN AUTOMATIC SOFTWARE RECHARGING METHOD AND AN AUTOMATIC SOFTWARE RECHARGING DEVICE|
    FR2990531B1|2012-05-11|2014-06-06|Airbus Operations Sas|METHOD FOR UPDATING AN AIRCRAFT SOFTWARE ABOARD AN AIRCRAFT|
    FR2992081B1|2012-06-15|2015-05-15|Thales Sa|ELECTRONIC SYSTEM COMPRISING A PLURALITY OF ELECTRONIC EQUIPMENT, ELECTRONIC EQUIPMENT OF SUCH A SYSTEM AND METHOD OF MANAGING AND MAINTAINING SUCH A SYSTEM|
    US9098374B2|2013-02-25|2015-08-04|Hamilton Sundstrand Corporation|Version control for software configurable aircraft systems|
    FR3003365B1|2013-03-12|2015-04-10|Airbus Operations Sas|METHOD AND DEVICE FOR MANAGING SOFTWARE UPDATES OF A SET OF EQUIPMENT OF A SYSTEM SUCH AS A SYSTEM OF AN AIRCRAFT|
    FR3004566B1|2013-04-16|2016-07-29|Airbus |MASTER AND SLAVE RADIO LABELS FOR EQUIPMENT MANAGEMENT SYSTEM AND METHOD|
    KR101548953B1|2013-12-24|2015-09-01|현대자동차주식회사|Method and apparatus for updating information for vehicle|US9916701B2|2014-09-10|2018-03-13|The Boeing Company|Vehicle auditing and control of maintenance and diagnosis for vehicle systems|
    US9507982B2|2015-01-06|2016-11-29|Honeywell International Inc.|Line replaceable unit health nodes and methods for determining maintenance actions relating to line replaceable units|
    US10318451B2|2016-06-30|2019-06-11|Ge Aviation Systems Llc|Management of data transfers|
    US10681132B2|2016-06-30|2020-06-09|Ge Aviation Systems Llc|Protocol for communicating engine data to wireless communication unit|
    US10467016B2|2016-06-30|2019-11-05|General Electric Company|Managing an image boot|
    US10444748B2|2016-06-30|2019-10-15|Ge Aviation Systems Llc|In-situ measurement logging by wireless communication unit for communicating engine data|
    US10712377B2|2016-06-30|2020-07-14|Ge Aviation Systems Llc|Antenna diagnostics for wireless communication unit for communicating engine data|
    US10819601B2|2016-06-30|2020-10-27|Ge Aviation Systems Llc|Wireless control unit server for conducting connectivity test|
    US10470114B2|2016-06-30|2019-11-05|General Electric Company|Wireless network selection|
    US10200110B2|2016-06-30|2019-02-05|Ge Aviation Systems Llc|Aviation protocol conversion|
    US10764747B2|2016-06-30|2020-09-01|Ge Aviation Systems Llc|Key management for wireless communication system for communicating engine data|
    US10529150B2|2016-06-30|2020-01-07|Aviation Systems LLC|Remote data loading for configuring wireless communication unit for communicating engine data|
    CN107454129A|2016-12-27|2017-12-08|亿航智能设备（广州）有限公司|Firmware upgrade method, device and system|
    FR3099574B1|2019-07-31|2021-10-15|Safran Aircraft Engines|Automatic detection of a hardware configuration of equipment on board an aircraft|
    法律状态:
    2015-09-22| PLFP| Fee payment|Year of fee payment: 2 |
    2016-04-01| PLSC| Search report ready|Effective date: 20160401 |
    2016-09-21| PLFP| Fee payment|Year of fee payment: 3 |
    2017-09-28| PLFP| Fee payment|Year of fee payment: 4 |
    2018-09-24| PLFP| Fee payment|Year of fee payment: 5 |
    2019-09-25| PLFP| Fee payment|Year of fee payment: 6 |
    2020-09-14| PLFP| Fee payment|Year of fee payment: 7 |
    2021-09-21| PLFP| Fee payment|Year of fee payment: 8 |
    优先权:
    申请号 | 申请日 | 专利标题
    FR1459125A|FR3026509B1|2014-09-26|2014-09-26|AUTOMATIC SOFTWARE RECHARGING ON ONBOARD EQUIPMENT|FR1459125A| FR3026509B1|2014-09-26|2014-09-26|AUTOMATIC SOFTWARE RECHARGING ON ONBOARD EQUIPMENT|
    US14/864,352| US9612819B2|2014-09-26|2015-09-24|System and method for automatic reloading of software into embarked equipment|
    [返回顶部]